| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CP.9.2.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.9.2 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | CP_9_2_Capture_Health_Service_Report_Information |
| Title | CP.9.2 Capture Health Service Report Information (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Support the creation of health service reports to authorized health entities that a provider may be required to generate (e.g., the creation of an oncologist's report that must be submitted to a national cancer registry). |
| Purpose | Providers are prompted to collect sufficient information in the course of care to avoid duplicate, retrospective or other additional data entry as part of supporting health management programs and reporting, for example public health, such as notifiable condition reports, immunization, cancer registry and discharge data. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Support the creation of health service reports to authorized health entities that a provider may be required to generate (e.g., the creation of an oncologist's report that must be submitted to a national cancer registry).
Providers are prompted to collect sufficient information in the course of care to avoid duplicate, retrospective or other additional data entry as part of supporting health management programs and reporting, for example public health, such as notifiable condition reports, immunization, cancer registry and discharge data.
| CP.9.2#01 | MAY |
The system MAY render a notification that prompts providers on the data needed for end of encounter reporting during the continuum of care to streamline end of care data collection. |
| CP.9.2#02 | SHOULD |
The system SHOULD provide the ability to render service reports at the completion of an episode of care (e.g., discharge summaries or public health reports) using data collected during the encounter. |
| CP.9.2#03 | conditional MAY |
IF the patient is tagged as deceased, THEN the system MAY provide the ability to capture (i.e., trigger) and render the collection of death certificate data. |
| CP.9.2#04 | SHOULD |
The system SHOULD provide the ability to capture and render the acknowledgement that health service reports have been received. |
| CP.9.2#05 | SHALL |
The system SHALL conform to function [[CP.9.1]] (Produce a Summary Record of Care). |
| CP.9.2#06 | SHOULD |
The system SHOULD render a notification that prompts providers on the information needed for regulatory safety reporting. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-CP.9.2",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Support the creation of health service reports to authorized health entities that a provider may be required to generate (e.g., the creation of an oncologist's report that must be submitted to a national cancer registry).</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Providers are prompted to collect sufficient information in the course of care to avoid duplicate, retrospective or other additional data entry as part of supporting health management programs and reporting, for example public health, such as notifiable condition reports, immunization, cancer registry and discharge data.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.9.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY render a notification that prompts providers on the data needed for end of encounter reporting during the continuum of care to streamline end of care data collection.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.9.2#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render service reports at the completion of an episode of care (e.g., discharge summaries or public health reports) using data collected during the encounter.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.9.2#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n <i>conditional</i>\n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF the patient is tagged as deceased, THEN the system MAY provide the ability to capture (i.e., trigger) and render the collection of death certificate data.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.9.2#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and render the acknowledgement that health service reports have been received.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.9.2#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to function [[CP.9.1]] (Produce a Summary Record of Care).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.9.2#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD render a notification that prompts providers on the information needed for regulatory safety reporting.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.9.2",
"version" : "2.1.0",
"name" : "CP_9_2_Capture_Health_Service_Report_Information",
"title" : "CP.9.2 Capture Health Service Report Information (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Support the creation of health service reports to authorized health entities that a provider may be required to generate (e.g., the creation of an oncologist's report that must be submitted to a national cancer registry).",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "Providers are prompted to collect sufficient information in the course of care to avoid duplicate, retrospective or other additional data entry as part of supporting health management programs and reporting, for example public health, such as notifiable condition reports, immunization, cancer registry and discharge data.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.9.2-01",
"label" : "CP.9.2#01",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY render a notification that prompts providers on the data needed for end of encounter reporting during the continuum of care to streamline end of care data collection.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.3.6#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.9.2-02",
"label" : "CP.9.2#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render service reports at the completion of an episode of care (e.g., discharge summaries or public health reports) using data collected during the encounter.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.3.6#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.9.2-03",
"label" : "CP.9.2#03",
"conformance" : [
"MAY"
],
"conditionality" : true,
"requirement" : "IF the patient is tagged as deceased, THEN the system MAY provide the ability to capture (i.e., trigger) and render the collection of death certificate data."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.9.2-04",
"label" : "CP.9.2#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and render the acknowledgement that health service reports have been received."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.9.2-05",
"label" : "CP.9.2#05",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL conform to function [[CP.9.1]] (Produce a Summary Record of Care)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.9.2-06",
"label" : "CP.9.2#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD render a notification that prompts providers on the information needed for regulatory safety reporting."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.